Skip to content

fix(deps): update dependency graphql to v17#1495

Merged
renovate[bot] merged 1 commit into
mainfrom
renovate/graphql-17.x
Jun 15, 2026
Merged

fix(deps): update dependency graphql to v17#1495
renovate[bot] merged 1 commit into
mainfrom
renovate/graphql-17.x

Conversation

@renovate

@renovate renovate Bot commented Jun 15, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
graphql ^0.12.0 || ^0.13.0 || ^14.0.0 || ^15.0.0 || ^16.0.0^0.12.0 || ^0.13.0 || ^14.0.0 || ^15.0.0 || ^16.0.0 || ^17.0.0 age confidence
graphql ^16.6.0^17.0.0 age confidence

Release Notes

graphql/graphql-js (graphql)

v17.0.0

Compare Source

v17.0.0 (2026-06-15)

New Feature 🚀
Bug Fix 🐞
Docs 📝
11 PRs were merged
Polish 💅
2 PRs were merged
Internal 🏠
6 PRs were merged
Committers: 3

Configuration

📅 Schedule: (in timezone Asia/Tokyo)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot enabled auto-merge (squash) June 15, 2026 23:08
@renovate

renovate Bot commented Jun 15, 2026

Copy link
Copy Markdown
Contributor Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml
? Verifying lockfile against supply-chain policies (832 entries)...
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 8, reused 0, downloaded 0, added 0
Progress: resolved 10, reused 0, downloaded 0, added 0
Progress: resolved 14, reused 0, downloaded 0, added 0
Progress: resolved 15, reused 0, downloaded 0, added 0
Progress: resolved 16, reused 0, downloaded 0, added 0
Progress: resolved 17, reused 0, downloaded 1, added 0
[WARN] Request took 11077ms: https://registry.npmjs.org/typescript
Progress: resolved 18, reused 0, downloaded 1, added 0
[WARN] Request took 10999ms: https://registry.npmjs.org/@graphql-codegen%2Fadd
[WARN] Request took 11111ms: https://registry.npmjs.org/@graphql-codegen%2Fcore
[WARN] Request took 11465ms: https://registry.npmjs.org/@graphql-codegen%2Fschema-ast
[WARN] Request took 11958ms: https://registry.npmjs.org/@graphql-codegen%2Fschema-ast
Progress: resolved 19, reused 0, downloaded 1, added 0
[WARN] Request took 12581ms: https://registry.npmjs.org/@graphql-codegen%2Fplugin-helpers
[WARN] Request took 12545ms: https://registry.npmjs.org/@graphql-codegen%2Fplugin-helpers
[WARN] Request took 13224ms: https://registry.npmjs.org/@graphql-codegen%2Ftypescript
Progress: resolved 21, reused 0, downloaded 1, added 0
[WARN] Request took 12961ms: https://registry.npmjs.org/@graphql-codegen%2Ftypescript
[WARN] Request took 13463ms: https://registry.npmjs.org/@graphql-codegen%2Ftypescript-operations
[WARN] Request took 13538ms: https://registry.npmjs.org/@graphql-codegen%2Fvisitor-plugin-common
[WARN] Request took 14337ms: https://registry.npmjs.org/@graphql-codegen%2Fvisitor-plugin-common
Progress: resolved 22, reused 0, downloaded 1, added 0
[WARN] Request took 14716ms: https://registry.npmjs.org/@graphql-codegen%2Fcli
Progress: resolved 117, reused 0, downloaded 1, added 0
[WARN] Request took 16119ms: https://registry.npmjs.org/@graphql-codegen%2Fcli
✗ Lockfile failed supply-chain policy check (832 entries in 16.8s)
[ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 8 lockfile entries failed verification:
  @vitest/expect@4.1.9 was published at 2026-06-15T07:02:01.000Z, within the minimumReleaseAge cutoff (2026-06-14T23:08:11.314Z)
  @vitest/mocker@4.1.9 was published at 2026-06-15T07:01:52.000Z, within the minimumReleaseAge cutoff (2026-06-14T23:08:11.314Z)
  @vitest/pretty-format@4.1.9 was published at 2026-06-15T07:01:42.000Z, within the minimumReleaseAge cutoff (2026-06-14T23:08:11.314Z)
  @vitest/runner@4.1.9 was published at 2026-06-15T07:01:55.000Z, within the minimumReleaseAge cutoff (2026-06-14T23:08:11.314Z)
  @vitest/snapshot@4.1.9 was published at 2026-06-15T07:01:58.000Z, within the minimumReleaseAge cutoff (2026-06-14T23:08:11.314Z)
  @vitest/spy@4.1.9 was published at 2026-06-15T07:01:45.000Z, within the minimumReleaseAge cutoff (2026-06-14T23:08:11.314Z)
  @vitest/utils@4.1.9 was published at 2026-06-15T07:01:49.000Z, within the minimumReleaseAge cutoff (2026-06-14T23:08:11.314Z)
  vitest@4.1.9 was published at 2026-06-15T07:02:10.000Z, within the minimumReleaseAge cutoff (2026-06-14T23:08:11.314Z)

The lockfile contains entries that the active policies reject. This can mean the lockfile is stale, or that someone committed a lockfile that bypassed the policy locally — inspect recent changes to pnpm-lock.yaml before trusting it. If the changes look expected, run "pnpm clean --lockfile" and then "pnpm install" to rebuild from a fresh resolution. Alternatively, relax the policy that flagged them.
Progress: resolved 159, reused 0, downloaded 1, added 0

@renovate renovate Bot merged commit 57553c8 into main Jun 15, 2026
0 of 3 checks passed
@renovate renovate Bot deleted the renovate/graphql-17.x branch June 15, 2026 23:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants